Configuration of Playback Device Audio Settings

ABSTRACT

Example techniques describe may facilitate a playback device applying a determined audio setting. An example implementation involves a first playback device receiving, over an unsecure network, a message indicating that a second playback device is available to join a playback network, wherein the first playback device is connected to the playback network. Based on a pre-existing configuration table, the first playback device determines an audio setting corresponding to a playback configuration for the second playback device, the playback configuration including the second playback device playing back audio synchronously with the first playback device in the playback network. The first playback device transmits, to the second playback device, one or more messages instructing the second playback device to apply the determined audio setting upon joining the playback network. Applying the determined audio setting includes forming the playback configuration with the first playback device to play back audio synchronously.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority under 35 U.S.C. § 120 to, and is acontinuation of, U.S. non-provisional patent application Ser. No.14/958,598, filed on Dec. 3, 2015, entitled “Configuration of PlaybackDevice Audio Settings,” which is incorporated herein by reference in itsentirety.

U.S. non-provisional patent application Ser. No. 16/180,952 claimspriority under 35 U.S.C. § 120 to, and is a continuation of, U.S.non-provisional patent application Ser. No. 13/767,850, filed on Feb.14, 2013, entitled “Automatic Configuration of Household PlaybackDevices,” and issued as U.S. Pat. No. 9,237,384 on Jan. 12, 2016, whichis incorporated herein by reference in its entirety.

FIELD OF THE DISCLOSURE

The disclosure is related to consumer goods and, more particularly, tosystems, products, features, services, and other items directed to mediaplayback or some aspect thereof.

BACKGROUND

Technological advancements have increased the accessibility of musiccontent, as well as other types of media, such as television content,movies, and interactive content. For example, a user can access audio,video, or both audio and video content over the Internet through anonline store, an Internet radio station, a music service, a movieservice, and so on, in addition to the more traditional avenues ofaccessing audio and video content. Demand for audio, video, and bothaudio and video content inside and outside of the home continues toincrease.

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and advantages of the presently disclosed technologymay be better understood with regard to the following description,appended claims, and accompanying drawings where:

FIG. 1 shows an example configuration in which certain embodiments maybe practiced;

FIG. 2A shows an illustration of an example zone player having abuilt-in amplifier and transducers;

FIG. 2B shows an illustration of an example zone player having abuilt-in amplifier and connected to external speakers;

FIG. 2C shows an illustration of an example zone player connected to anA/V receiver and speakers;

FIG. 3 shows an illustration of an example controller;

FIG. 4 shows an internal functional block diagram of an example zoneplayer;

FIG. 5 shows an internal functional block diagram of an examplecontroller;

FIG. 6 shows an example ad-hoc playback network;

FIG. 7 shows a system including a plurality of networks including acloud-based network and at least one local playback network;

FIG. 8A shows a first example flow diagram for automatically adding aplayback device to a secure playback network;

FIG. 8B shows a second example flow diagram for automatically adding aplayback device to a secure network;

FIG. 8C shows an example flow diagram for automatically configuring aplayback device in a playback network.

FIG. 9A shows a first scenario for adding a playback device to, andconfiguring the playback device for a secure playback network;

FIG. 9B shows a second scenario for adding a playback device to, andconfiguring the playback device for a secure playback network;

FIG. 9C shows a third scenario for adding a playback device to, andconfiguring the playback device for a secure playback network; and

FIG. 10 shows an example interaction between devices when adding aplayback device to, and configuring the playback device for a secureplayback network of devices.

In addition, the drawings are for the purpose of illustrating exampleembodiments, but it is understood that the inventions are not limited tothe arrangements and instrumentality shown in the drawings.

DETAILED DESCRIPTION I. Overview

Embodiments are described herein that may cause a playback device to beadded to a secure network for media playback, and further cause theplayback device to be configured. In particular, the embodiments maycause the playback device to be automatically added to the securenetwork without any action from a user. Further, upon joining the securenetwork, the playback device may be automatically configured to rendermedia in synchrony with other playback devices in the secure network.

In one example, the user may acquire a new playback device to rendermedia in synchrony with other playback devices that may already beconfigured to render media in synchrony within a secure network. In onecase, upon powering up the new playback device, the new playback devicemay send out a join message indicating that the new playback device isavailable to join the secure network. If the new playback device iswithin communicative range of a device in the secure network, the joinmessage may be received by the device within the secure network. Thedevice may be another playback device or a controller device. Inresponse to receiving the join message indicating that the new playbackdevice is available to join the secure network, the device in the securenetwork may then transmit security parameters to the new playback devicethat can be used for the new playback device to join the secure network.

In another example, one or more devices in the secure network may beanticipating the join message from the new playback device indicatingthat the new playback device is available to join the secure network.For instance, the controller device may receive a configuration tablelisting all devices permitted to join the secure network. As such, if adevice listed in the configuration is not already in the network, thecontroller device (and/or other devices in the secure network) may“listen” for the join message from the new playback device. In thiscase, the configuration table may also list the security parameters thatmay subsequently be sent to the new playback device for the new playbackdevice to join the secure network.

In addition to the security parameters, the configuration table may alsoinclude configuration data or setup information for the new playbackdevice, indicating how the new playback device should be configured forplayback. For instance, if the new playback device is intended for useas one of a stereo pair to render media in synchrony with another devicein the secure network, the configuration data may indicate that the newplayback device will function as either a left or right channel speaker.

In one case, the new playback device may send a configuration message tothe controller device (and/or other devices in the secure network)indicating that the new playback device is available or ready to beconfigured. In one instance, the configuration message may be receivedtogether with the join message (as a single communication instance). Inanother instance, the configuration message may be received after thejoin message, or after the new playback device has joined the securenetwork. In either instance, the configuration data may be communicatedto the new playback device upon receiving the configuration message, andthe new playback device may then be configured according to theconfiguration data.

In one example, the configuration table, which may include both securityparameters for joining a secure network and configuration data forsetting up a playback device, may be provided to the controller deviceand/or other devices in the secure network by a server, such as one froma “cloud” service over the Internet. In one case, the securityparameters and configuration data may be, to an extent, determined basedon previous input from the user. For instance, when a user acquires anew playback device, whether at a local store or over the World WideWeb, the user may be prompted to enter some identifying information andasked to answer some questions relating to how the user plans to use thenew playback device. The identifying information provided by the usermay indicate the secure network to which the user wishes to add the newplayback device and may therefore be used to identify or determine thesecurity parameters to be used by the new playback device to join thesecure network. Similarly, the answers to the questions may indicate howthe new playback device will be used and may therefore be used togenerate configuration data that may be used to configure the newplayback device for playback.

As suggested above, the present application involves causing a newplayback device to be automatically added to a secure network andconfigured to render media, possibly in synchrony with other devices inthe secure network, without any action by a user. In one aspect, amethod is provided. The method involves receiving, by a controllerdevice, a configuration table from a server over a wide area network,determining, by the controller device, that the configuration tableincludes an entry corresponding to the playback device that isunconfigured for playback, and responsively, transmitting from thecontroller device to the playback device, a first message comprisingsetup information for the playback device.

In another aspect, a controller device is provided. The controllerdevice includes processor, memory, and instructions stored on thememory. The instructions are executable by the processor to performfunctions including receiving a configuration table from a server over awide area network, determining that the configuration table includes anentry corresponding to the playback device that is unconfigured forplayback, and responsively, transmitting to the playback device, a firstmessage comprising setup information for the playback device.

In yet another aspect, a non-transitory computer readable medium havinginstructions stored thereon is provided. The instructions are executableby a computing device to cause the computing device to perform functionsincluding receiving, by a controller device, a configuration table froma server over a wide area network, determining, by the controllerdevice, that the configuration table includes an entry corresponding tothe playback device that is unconfigured for playback, and responsivelytransmitting, by the controller device to the playback device, a firstmessage comprising setup information for the playback device.

Other embodiments, as those discussed in the following and others as canbe appreciated by one having ordinary skill in the art are alsopossible.

II. Example Operating Environment

Referring now to the drawings, in which like numerals can refer to likeparts throughout the figures, FIG. 1 shows an example media systemconfiguration 100 in which one or more embodiments disclosed herein canbe practiced or implemented.

By way of illustration, the media system configuration 100 represents ahome with multiple zones, though the home could have been configuredwith only one zone. Each zone, for example, may represent a differentroom or space, such as an office, bathroom, bedroom, kitchen, diningroom, family room, home theater room, utility or laundry room, andpatio. A single zone might also include multiple rooms or spaces if soconfigured. One or more of zone players 102-124 are shown in eachrespective zone. A zone player 102-124, also referred to as a playbackdevice, multimedia unit, speaker, player, and so on, provides audio,video, and/or audiovisual output. A controller 130 (e.g., shown in thekitchen for purposes of illustration) provides control to the mediasystem configuration 100. Controller 130 may be fixed to a zone, oralternatively, mobile such that it can be moved about the zones. Themedia system configuration 100 may also include more than one controller130. The media system configuration 100 illustrates an example wholehouse media system, though it is understood that the technologydescribed herein is not limited to its particular place of applicationor to an expansive system like a whole house media system 100 of FIG. 1.

a. Example Zone Players

FIGS. 2A, 2B, and 2C show example types of zone players. Zone players200, 202, and 204 of FIGS. 2A, 2B, and 2C, respectively, can correspondto any of the zone players 102-124 of FIG. 1, for example. In someembodiments, audio is reproduced using only a single zone player, suchas by a full-range player. In some embodiments, audio is reproducedusing two or more zone players, such as by using a combination offull-range players or a combination of full-range and specializedplayers. In some embodiments, zone players 200-204 may also be referredto as a “smart speaker,” because they contain processing capabilitiesbeyond the reproduction of audio, more of which is described below.

FIG. 2A illustrates zone player 200 that includes sound producingequipment 208 capable of reproducing full-range sound. The sound maycome from an audio signal that is received and processed by zone player200 over a wired or wireless data network. Sound producing equipment 208includes one or more built-in amplifiers and one or more acoustictransducers (e.g., speakers). A built-in amplifier is described morebelow with respect to FIG. 4. A speaker or acoustic transducer caninclude, for example, any of a tweeter, a mid-range driver, a low-rangedriver, and a subwoofer. In some embodiments, zone player 200 can bestatically or dynamically configured to play stereophonic audio,monaural audio, or both. In some embodiments, zone player 200 isconfigured to reproduce a subset of full-range sound, such as when zoneplayer 200 is grouped with other zone players to play stereophonicaudio, monaural audio, and/or surround audio or when the audio contentreceived by zone player 200 is less than full-range.

FIG. 2B illustrates zone player 202 that includes a built-in amplifierto power a set of detached speakers 210. A detached speaker can include,for example, any type of loudspeaker. Zone player 202 may be configuredto power one, two, or more separate loudspeakers. Zone player 202 may beconfigured to communicate an audio signal (e.g., right and left channelaudio or more channels depending on its configuration) to the detachedspeakers 210 via a wired path.

FIG. 2C illustrates zone player 204 that does not include a built-inamplifier, but is configured to communicate an audio signal, receivedover a data network, to an audio (or “audio/video”) receiver 214 withbuilt-in amplification.

Referring back to FIG. 1, in some embodiments, one, some, or all of thezone players 102 to 124 can retrieve audio directly from a source. Forexample, a zone player may contain a playlist or queue of audio items tobe played (also referred to herein as a “playback queue”). Each item inthe queue may comprise a uniform resource identifier (URI) or some otheridentifier. The URI or identifier can point the zone player to the audiosource. The source might be found on the Internet (e.g., the cloud),locally from another device over data network 128 (described furtherbelow), from the controller 130, stored on the zone player itself, orfrom an audio source communicating directly to the zone player. In someembodiments, the zone player can reproduce the audio itself, send it toanother zone player for reproduction, or both where the audio is playedby the zone player and one or more additional zone players in synchrony.In some embodiments, the zone player can play a first audio content (ornot play at all), while sending a second, different audio content toanother zone player(s) for reproduction.

By way of illustration, SONOS, Inc. of Santa Barbara, Calif. presentlyoffers for sale zone players referred to as a “PLAY:5,” “PLAY:3,”“CONNECT:AMP,” “CONNECT,” and “SUB.” Any other past, present, and/orfuture zone players can additionally or alternatively be used toimplement the zone players of example embodiments disclosed herein.Additionally, it is understood that a zone player is not limited to theparticular examples illustrated in FIGS. 2A, 2B, and 2C or to the SONOSproduct offerings. For example, a zone player may include a wired orwireless headphone. In yet another example, a zone player might includea sound bar for television. In yet another example, a zone player caninclude or interact with a docking station for an Apple IPOD™ or similardevice.

b. Example Controllers

FIG. 3 illustrates an example wireless controller 300 in docking station302. By way of illustration, controller 300 may correspond tocontrolling device 130 of FIG. 1. Docking station 302, if provided, maybe used to charge a battery of controller 300. In some embodiments,controller 300 may be provided with a touch screen 304 that allows auser to interact through touch with the controller 300, for example, toretrieve and navigate a playlist of audio items, control operations ofone or more zone players, and provide overall control of the systemconfiguration 100. In certain embodiments, any number of controllers canbe used to control the system configuration 100. In some embodiments,there may be a limit set on the number of controllers that can controlthe system configuration 100. The controllers might be wireless likewireless controller 300 or wired to data network 128.

In some embodiments, if more than one controller is used in system 100,each controller may be coordinated to display common content, and mayall be dynamically updated to indicate changes made from a singlecontroller. Coordination can occur, for instance, by a controllerperiodically requesting a state variable directly or indirectly from oneor more zone players; the state variable may provide information aboutsystem 100, such as current zone group configuration, what is playing inone or more zones, volume levels, and other items of interest. The statevariable may be passed around on data network 128 between zone players(and controllers, if so desired) as needed or as often as programmed.

In addition, an application running on any network-enabled portabledevice, such as an IPHONE™ IPAD™ ANDROID™ powered phone, or any othersmart phone or network-enabled device can be used as controller 130. Anapplication running on a laptop or desktop personal computer (PC) orMac™ can also be used as controller 130. Such controllers may connect tosystem 100 through an interface with data network 128, a zone player, awireless router, or using some other configured connection path. Examplecontrollers offered by Sonos, Inc. of Santa Barbara, Calif. include a“Controller 200,” “SONOS® CONTROL,” “SONOS® Controller for IPHONE™,”“SONOS® Controller for IPAD™,” “SONOS® Controller for ANDROID™,” “SONOS®Controller for MAC™ or PC.”

c. Example Data Connection

Zone players 102 to 124 of FIG. 1 are coupled directly or indirectly toa data network, such as data network 128. Controller 130 may also becoupled directly or indirectly to data network 128 or individual zoneplayers. Data network 128 is represented by an octagon in the figure tostand out from other representative components. While data network 128is shown in a single location, it is understood that such a network isdistributed in and around system 100. Particularly, data network 128 canbe a wired network, a wireless network, or a combination of both wiredand wireless networks. In some embodiments, one or more of the zoneplayers 102-124 are wirelessly coupled to data network 128 based on aproprietary mesh network. In some embodiments, one or more of the zoneplayers 102-124 are wirelessly coupled to data network 128 using anon-mesh topology. In some embodiments, one or more of the zone players102-124 are coupled via a wire to data network 128 using Ethernet orsimilar technology. In addition to the one or more zone players 102-124connecting to data network 128, data network 128 can further allowaccess to a wide area network, such as the Internet.

In some embodiments, connecting any of the zone players 102-124, or someother connecting device, to a broadband router, can create data network128. Other zone players 102-124 can then be added wired or wirelessly tothe data network 128. For example, a zone player (e.g., any of zoneplayers 102-124) can be added to the system configuration 100 by simplypressing a button on the zone player itself (or perform some otheraction), which enables a connection to be made to data network 128. Thebroadband router can be connected to an Internet Service Provider (ISP),for example. The broadband router can be used to form another datanetwork within the system configuration 100, which can be used in otherapplications (e.g., web surfing). Data network 128 can also be used inother applications, if so programmed. An example, second network mayimplement SONOSNET™ protocol, developed by SONOS, Inc. of Santa Barbara.SONOSNET™ represents a secure, AES-encrypted, peer-to-peer wireless meshnetwork. Alternatively, in certain embodiments, the data network 128 isthe same network, such as a traditional wired or wireless network, usedfor other applications in the household.

d. Example Zone Configurations

A particular zone can contain one or more zone players. For example, thefamily room of FIG. 1 contains two zone players 106 and 108, while thekitchen is shown with one zone player 102. In another example, the hometheater room contains additional zone players to play audio from a 5.1channel or greater audio source (e.g., a movie encoded with 5.1 orgreater audio channels). In some embodiments, one can position a zoneplayer in a room or space and assign the zone player to a new orexisting zone via controller 130. As such, zones may be created,combined with another zone, removed, and given a specific name (e.g.,“Kitchen”), if so desired and programmed to do so with controller 130.Moreover, in some embodiments, zone configurations may be dynamicallychanged even after being configured using controller 130 or some othermechanism.

In some embodiments, if a zone contains two or more zone players, suchas the two zone players 106 and 108 in the family room, then the twozone players 106 and 108 can be configured to play the same audio sourcein synchrony, or the two zone players 106 and 108 can be paired to playtwo separate sounds in left and right channels, for example. In otherwords, the stereo effects of a sound can be reproduced or enhancedthrough the two zone players 106 and 108, one for the left sound and theother for the right sound. In certain embodiments, paired zone players(also referred to as “bonded zone players”) can play audio in synchronywith other zone players in the same or different zones.

In some embodiments, two or more zone players can be sonicallyconsolidated to form a single, consolidated zone player. A consolidatedzone player (though made up of multiple, separate devices) can beconfigured to process and reproduce sound differently than anunconsolidated zone player or zone players that are paired, because aconsolidated zone player will have additional speaker drivers from whichsound can be passed. The consolidated zone player can further be pairedwith a single zone player or yet another consolidated zone player. Eachplayback device of a consolidated playback device can be set in aconsolidated mode, for example.

According to some embodiments, one can continue to do any of: group,consolidate, and pair zone players, for example, until a desiredconfiguration is complete. The actions of grouping, consolidation, andpairing are preferably performed through a control interface, such asusing controller 130, and not by physically connecting and re-connectingspeaker wire, for example, to individual, discrete speakers to createdifferent configurations. As such, certain embodiments described hereinprovide a more flexible and dynamic platform through which soundreproduction can be offered to the end-user.

e. Example Audio Sources

In some embodiments, each zone can play from the same audio source asanother zone or each zone can play from a different audio source. Forexample, someone can be grilling on the patio and listening to jazzmusic via zone player 124, while someone is preparing food in thekitchen and listening to classical music via zone player 102. Further,someone can be in the office listening to the same jazz music via zoneplayer 110 that is playing on the patio via zone player 124. In someembodiments, the jazz music played via zone players 110 and 124 isplayed in synchrony. Synchronizing playback amongst zones allows forsomeone to pass through zones while seamlessly (or substantiallyseamlessly) listening to the audio. Further, zones can be put into a“party mode” such that all associated zones will play audio insynchrony.

Sources of audio content to be played by zone players 102-124 arenumerous. In some embodiments, music on a zone player itself may beaccessed and a played. In some embodiments, music from a personallibrary stored on a computer or networked-attached storage (NAS) may beaccessed via the data network 128 and played. In some embodiments,Internet radio stations, shows, and podcasts can be accessed via thedata network 128. Music or cloud services that let a user stream and/ordownload music and audio content can be accessed via the data network128. Further, music can be obtained from traditional sources, such as aturntable or CD player, via a line-in connection to a zone player, forexample. Audio content can also be accessed using a different protocol,such as AIRPLAY™, which is a wireless technology by Apple, Inc., forexample. Audio content received from one or more sources can be sharedamongst the zone players 102 to 124 via data network 128 and/orcontroller 130. The above-disclosed sources of audio content arereferred to herein as network-based audio information sources. However,network-based audio information sources are not limited thereto.

In some embodiments, the example home theater zone players 116, 118, 120are coupled to an audio information source such as a television 132. Insome examples, the television 132 is used as a source of audio for thehome theater zone players 116, 118, 120, while in other examples audioinformation from the television 132 can be shared with any of the zoneplayers 102-124 in the audio system 100.

III. Example Zone Players

Referring now to FIG. 4, there is shown an example block diagram of azone player 400 in accordance with an embodiment. Zone player 400includes a network interface 402, a processor 408, a memory 410, anaudio processing component 412, one or more modules 414, an audioamplifier 416, and a speaker unit 418 coupled to the audio amplifier416. FIG. 2A shows an example illustration of such a zone player. Othertypes of zone players may not include the speaker unit 418 (e.g., suchas shown in FIG. 2B) or the audio amplifier 416 (e.g., such as shown inFIG. 2C). Further, it is contemplated that the zone player 400 can beintegrated into another component. For example, the zone player 400could be constructed as part of a television, lighting, or some otherdevice for indoor or outdoor use.

In some embodiments, network interface 402 facilitates a data flowbetween zone player 400 and other devices on a data network 128. In someembodiments, in addition to getting audio from another zone player ordevice on data network 128, zone player 400 may access audio directlyfrom the audio source, such as over a wide area network or on the localnetwork. In some embodiments, the network interface 402 can furtherhandle the address part of each packet so that it gets to the rightdestination or intercepts packets destined for the zone player 400.Accordingly, in certain embodiments, each of the packets includes anInternet Protocol (IP)-based source address as well as an IP-baseddestination address.

In some embodiments, network interface 402 can include one or both of awireless interface 404 and a wired interface 406. The wireless interface404, also referred to as a radio frequency (RF) interface, providesnetwork interface functions for the zone player 400 to wirelesslycommunicate with other devices (e.g., other zone player(s), speaker(s),receiver(s), component(s) associated with the data network 128, and soon) in accordance with a communication protocol (e.g., any wirelessstandard including IEEE 802.11a, 802.11b, 802.11g, 802.11n, or 802.15).Wireless interface 404 may include one or more radios. To receivewireless signals and to provide the wireless signals to the wirelessinterface 404 and to transmit wireless signals, the zone player 400includes one or more antennas 420. The wired interface 406 providesnetwork interface functions for the zone player 400 to communicate overa wire with other devices in accordance with a communication protocol(e.g., IEEE 802.3). In some embodiments, a zone player includes multiplewireless 404 interfaces. In some embodiments, a zone player includesmultiple wired 406 interfaces. In some embodiments, a zone playerincludes both of the interfaces 404 and 406. In some embodiments, a zoneplayer 400 includes only the wireless interface 404 or the wiredinterface 406.

In some embodiments, the processor 408 is a clock-driven electronicdevice that is configured to process input data according toinstructions stored in memory 410. The memory 410 is data storage thatcan be loaded with one or more software module(s) 414, which can beexecuted by the processor 408 to achieve certain tasks. In theillustrated embodiment, the memory 410 is a tangible machine-readablemedium storing instructions that can be executed by the processor 408.In some embodiments, a task might be for the zone player 400 to retrieveaudio data from another zone player or a device on a network (e.g.,using a uniform resource locator (URL) or some other identifier). Insome embodiments, a task may be for the zone player 400 to send audiodata to another zone player or device on a network. In some embodiments,a task may be for the zone player 400 to synchronize playback of audiowith one or more additional zone players. In some embodiments, a taskmay be to pair the zone player 400 with one or more zone players tocreate a multi-channel audio environment. Additional or alternativetasks can be achieved via the one or more software module(s) 414 and theprocessor 408.

The audio processing component 412 can include one or moredigital-to-analog converters (DAC), an audio preprocessing component, anaudio enhancement component or a digital signal processor, and so on. Insome embodiments, the audio processing component 412 may be part ofprocessor 408. In some embodiments, the audio that is retrieved via thenetwork interface 402 is processed and/or intentionally altered by theaudio processing component 412. Further, the audio processing component412 can produce analog audio signals. The processed analog audio signalsare then provided to the audio amplifier 416 for play back throughspeakers 418. In addition, the audio processing component 412 caninclude circuitry to process analog or digital signals as inputs to playfrom zone player 400, send to another zone player on a network, or bothplay and send to another zone player on the network. An example inputincludes a line-in connection (e.g., an auto-detecting 3.5 mm audioline-in connection).

The audio amplifier 416 is a device(s) that amplifies audio signals to alevel for driving one or more speakers 418. The one or more speakers 418can include an individual transducer (e.g., a “driver”) or a completespeaker system that includes an enclosure including one or more drivers.A particular driver can be a subwoofer (e.g., for low frequencies), amid-range driver (e.g., for middle frequencies), and a tweeter (e.g.,for high frequencies), for example. An enclosure can be sealed orported, for example. Each transducer may be driven by its own individualamplifier.

A commercial example, presently known as the PLAY:5™, is a zone playerwith a built-in amplifier and speakers that is capable of retrievingaudio directly from the source, such as on the Internet or on the localnetwork, for example. In particular, the PLAY:5™ is a five-amp,five-driver speaker system that includes two tweeters, two mid-rangedrivers, and one woofer. When playing audio content via the PLAY:5, theleft audio data of a track is sent out of the left tweeter and leftmid-range driver, the right audio data of a track is sent out of theright tweeter and the right mid-range driver, and mono bass is sent outof the subwoofer. Further, both mid-range drivers and both tweeters havethe same equalization (or substantially the same equalization). That is,they are both sent the same frequencies but from different channels ofaudio. Audio from Internet radio stations, online music and videoservices, downloaded music, analog audio inputs, television, DVD, and soon, can be played from the PLAY:5™.

IV. Example Controller

Referring now to FIG. 5, there is shown an example block diagram forcontroller 500, which can correspond to the controlling device 130 inFIG. 1. Controller 500 can be used to facilitate the control ofmulti-media applications, automation and others in a system. Inparticular, the controller 500 may be configured to facilitate aselection of a plurality of audio sources available on the network andenable control of one or more zone players (e.g., the zone players102-124 in FIG. 1) through a wireless or wired network interface 508.According to one embodiment, the wireless communications is based on anindustry standard (e.g., infrared, radio, wireless standards includingIEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.15, and so on). Further,when a particular audio is being accessed via the controller 500 orbeing played via a zone player, a picture (e.g., album art) or any otherdata, associated with the audio and/or audio source can be transmittedfrom a zone player or other electronic device to controller 500 fordisplay.

Controller 500 is provided with a screen 502 and an input interface 514that allows a user to interact with the controller 500, for example, tonavigate a playlist of many multimedia items and to control operationsof one or more zone players. The screen 502 on the controller 500 can bean LCD screen, for example. The screen 500 communicates with and iscommanded by a screen driver 504 that is controlled by a microcontroller(e.g., a processor) 506. The memory 510 can be loaded with one or moreapplication modules 512 that can be executed by the microcontroller 506with or without a user input via the user interface 514 to achievecertain tasks. In some embodiments, an application module 512 isconfigured to facilitate grouping a number of selected zone players intoa zone group and synchronizing the zone players for audio play back. Insome embodiments, an application module 512 is configured to control theaudio sounds (e.g., volume) of the zone players in a zone group. Inoperation, when the microcontroller 506 executes one or more of theapplication modules 512, the screen driver 504 generates control signalsto drive the screen 502 to display an application specific userinterface accordingly.

The controller 500 includes a network interface 508 that facilitateswired or wireless communication with a zone player. In some embodiments,the commands such as volume control and audio playback synchronizationare sent via the network interface 508. In some embodiments, a savedzone group configuration is transmitted between a zone player and acontroller via the network interface 508. The controller 500 can controlone or more zone players, such as 102-124 of FIG. 1. There can be morethan one controller for a particular system, and each controller mayshare common information with another controller, or retrieve the commoninformation from a zone player, if such a zone player storesconfiguration data (e.g., such as a state variable). Further, acontroller can be integrated into a zone player.

It should be noted that other network-enabled devices such as an IPHONE™IPAD™ or any other smart phone or network-enabled device (e.g., anetworked computer such as a PC or MAC™) can also be used as acontroller to interact or control zone players in a particularenvironment. In some embodiments, a software application or upgrade canbe downloaded onto a network-enabled device to perform the functionsdescribed herein.

In certain embodiments, a user can create a zone group (also referred toas a bonded zone) including at least two zone players from thecontroller 500. The zone players in the zone group can play audio in asynchronized fashion, such that all of the zone players in the zonegroup play back an identical audio source or a list of identical audiosources in a synchronized manner such that no (or substantially no)audible delays or hiccups are to be heard. Similarly, in someembodiments, when a user increases the audio volume of the group fromthe controller 500, the signals or data of increasing the audio volumefor the group are sent to one of the zone players and causes other zoneplayers in the group to be increased together in volume.

A user via the controller 500 can group zone players into a zone groupby activating a “Link Zones” or “Add Zone” soft button, or de-grouping azone group by activating an “Unlink Zones” or “Drop Zone” button. Forexample, one mechanism for ‘joining’ zone players together for audioplay back is to link a number of zone players together to form a group.To link a number of zone players together, a user can manually link eachzone player or room one after the other. For example, assume that thereis a multi-zone system that includes the following zones: Bathroom,Bedroom, Den, Dining Room, Family Room, and Foyer.

In certain embodiments, a user can link any number of the six zoneplayers, for example, by starting with a single zone and then manuallylinking each zone to that zone.

In certain embodiments, a set of zones can be dynamically linkedtogether using a command to create a zone scene or theme (subsequent tofirst creating the zone scene). For instance, a “Morning” zone scenecommand can link the Bedroom, Office, and Kitchen zones together in oneaction. Without this single command, the user would manually andindividually link each zone. The single command may include a mouseclick, a double mouse click, a button press, a gesture, or some otherprogrammed action. Other kinds of zone scenes can be programmed.

In certain embodiments, a zone scene can be triggered based on time(e.g., an alarm clock function). For instance, a zone scene can be setto apply at 8:00 am. The system can link appropriate zonesautomatically, set specific music to play, and then stop the music aftera defined duration. Although any particular zone can be triggered to an“On” or “Off” state based on time, for example, a zone scene enables anyzone(s) linked to the scene to play a predefined audio (e.g., afavorable song, a predefined playlist) at a specific time and/or for aspecific duration. If, for any reason, the scheduled music failed to beplayed (e.g., an empty playlist, no connection to a share, failedUniversal Plug and Play (UPnP), no Internet connection for an InternetRadio station, and so on), a backup buzzer can be programmed to sound.The buzzer can include a sound file that is stored in a zone player, forexample.

V. Example Ad-Hoc Network

Certain particular examples are now provided in connection with FIG. 6to describe, for purposes of illustration, certain systems and methodsto provide and facilitate connection to a playback network. FIG. 6 showsthat there are three zone players 602, 604 and 606 and a controller 608that form a network branch that is also referred to as an Ad-Hoc network610. The network 610 may be wireless, wired, or a combination of wiredand wireless. In general, an Ad-Hoc (or “spontaneous”) network is alocal area network or other small network in which there is generally noone access point for all traffic. With an established Ad-Hoc network610, the devices 602, 604, 606 and 608 can all communicate with eachother in a “peer-to-peer” style of communication, for example.Furthermore, devices may join and/or leave from the network 610, and thenetwork 610 will automatically reconfigure itself without needing theuser to reconfigure the network 610. While an Ad-Hoc network isreferenced in FIG. 6, it is understood that a playback network may bebased on a type of network that is completely or partially differentfrom an Ad-Hoc network.

Using the Ad-Hoc network 610, the devices 602, 604, 606, and 608 canshare or exchange one or more audio sources and be dynamically groupedto play the same or different audio sources. For example, the devices602 and 604 are grouped to playback one piece of music, and at the sametime, the device 606 plays back another piece of music. In other words,the devices 602, 604, 606 and 608, as shown in FIG. 6, form a HOUSEHOLDthat distributes audio and/or reproduces sound. As used herein, the termHOUSEHOLD (provided in uppercase letters to disambiguate from the user'sdomicile) is used to represent a collection of networked devices thatare cooperating to provide an application or service. An instance of aHOUSEHOLD is identified with a household 610 (or household identifier),though a HOUSEHOLD may be identified with a different area or place.

In certain embodiments, a household identifier (HHID) is a short stringor an identifier that is computer-generated to help ensure that it isunique. Accordingly, the network 610 can be characterized by a uniqueHHID and a unique set of configuration variables or parameters, such aschannels (e.g., respective frequency bands), service set identifier(SSID) (a sequence of alphanumeric characters as a name of a wirelessnetwork), and WEP keys (wired equivalent privacy or other securitykeys). In certain embodiments, SSID is set to be the same as HHID.

In certain embodiments, each HOUSEHOLD includes two types of networknodes: a control point (CP) and a zone player (ZP). The control pointcontrols an overall network setup process and sequencing, including anautomatic generation of required network parameters (e.g., WEP keys). Inan embodiment, the CP also provides the user with a HOUSEHOLDconfiguration user interface. The CP function can be provided by acomputer running a CP application module, or by a handheld controller(e.g., the controller 308) also running a CP application module, forexample. The zone player is any other device on the network that isplaced to participate in the automatic configuration process. The ZP, asa notation used herein, includes the controller 308 or a computingdevice, for example. In some embodiments, the functionality, or certainparts of the functionality, in both the CP and the ZP are combined at asingle node (e.g., a ZP contains a CP or vice-versa).

In certain embodiments, configuration of a HOUSEHOLD involves multipleCPs and ZPs that rendezvous and establish a known configuration suchthat they can use a standard networking protocol (e.g., IP over Wired orWireless Ethernet) for communication. In an embodiment, two types ofnetworks/protocols are employed: Ethernet 802.3 and Wireless 802.11g.Interconnections between a CP and a ZP can use either of thenetworks/protocols. A device in the system as a member of a HOUSEHOLDcan connect to both networks simultaneously.

In an environment that has both networks in use, it is assumed that atleast one device in a system is connected to both as a bridging device,thus providing bridging services between wired/wireless networks forothers. The zone player 606 in FIG. 6 is shown to be connected to bothnetworks, for example. The connectivity to the network 612 is based onEthernet and/or Wireless, while the connectivity to other devices 602,604 and 608 is based on Wireless and Ethernet if so desired.

It is understood, however, that in some embodiments each zone player606, 604, 602 may access the Internet when retrieving media from thecloud (e.g., the Internet) via the bridging device. For example, zoneplayer 602 may contain a uniform resource locator (URL) that specifiesan address to a particular audio track in the cloud. Using the URL, thezone player 602 may retrieve the audio track from the cloud, andultimately play the audio out of one or more zone players.

VI. Example System Configuration

FIG. 7 shows a system including a plurality of networks including acloud-based network and at least one local playback network. A localplayback network includes a plurality of playback devices or players,though it is understood that the playback network may contain only oneplayback device. In certain embodiments, each player has an ability toretrieve its content for playback. Control and content retrieval can bedistributed or centralized, for example. Input can include streamingcontent provider input, third party application input, mobile deviceinput, user input, and/or other playback network input into the cloudfor local distribution and playback.

As illustrated by the example system 700 of FIG. 7, a plurality ofcontent providers 720-750 can be connected to one or more local playbacknetworks 760-770 via a cloud and/or other network 710. Using the cloud710, a multimedia audio system server 720 (e.g., Sonos™), a mobiledevice 730, a third party application 740, a content provider 750 and soon can provide multimedia content (requested or otherwise) to localplayback networks 760, 770. Within each local playback network 760, 770,a controller 762, 772 and a playback device 764, 774 can be used toplayback audio content.

VII. Example Automatic Connection and Configuration of a Playback Device

As discussed above, embodiments are described herein that may cause azone player to automatically be added to a secure network forsynchronized media playback, and further cause the zone player toautomatically be configured to render media in synchrony with otherplayback devices in the secure network.

FIG. 8A shows a first example flow diagram of a method 800 forautomatically adding a playback device to a secure playback network, inaccordance with at least some embodiments described herein. Method 800shown in FIG. 8A presents an embodiment of a method that could be usedin the environments 100, 600, and 700 with the systems 200, 202, 204,300, 400, and 500 for example, in communication with one or moredevices, such those illustrated in FIGS. 2-5. Method 800 may include oneor more operations, functions, or actions as illustrated by one or moreof blocks 802-808. Although the blocks are illustrated in sequentialorder, these blocks may also be performed in parallel, and/or in adifferent order than those described herein. Also, the various blocksmay be combined into fewer blocks, divided into additional blocks,and/or removed based upon the desired implementation.

In addition, for the method 800 and other processes and methodsdisclosed herein, the flowchart shows functionality and operation of onepossible implementation of present embodiments. In this regard, eachblock may represent a module, a segment, or a portion of program code,which includes one or more instructions executable by a processor forimplementing specific logical functions or steps in the process. Theprogram code may be stored on any type of computer readable medium, forexample, such as a storage device including a disk or hard drive. Thecomputer readable medium may include non-transitory computer readablemedium, for example, such as computer-readable media that stores datafor short periods of time like register memory, processor cache andRandom Access Memory (RAM). The computer readable medium may alsoinclude non-transitory media, such as secondary or persistent long termstorage, like read only memory (ROM), optical or magnetic disks,compact-disc read only memory (CD-ROM), for example. The computerreadable media may also be any other volatile or non-volatile storagesystems. The computer readable medium may be considered a computerreadable storage medium, for example, or a tangible storage device. Inaddition, for the method 800 and other processes and methods disclosedherein, each block in FIG. 8 may represent circuitry that is wired toperform the specific logical functions in the process.

At block 802, the method 800 may involve receiving a first message froma playback device indicating that the playback device is available tojoin a secure network for synchronized rendering of media. In somediscussions herein, the secure network of playback devices configured torender media in synchrony may also be referred to as a playback system.As mentioned above, a new zone player, upon being powered up, may sendout the first message, which may be a “join message,” for example,indicating that the zone player is available to join the secure networkfor media playback. The first message may also be other types ofmessages, such as an “alive message” announcing a presence of the newzone player. In this case, the alive message may implicitly indicatethat the new zone player is available to join the secure network. Thetransmission of the join message from the new zone player to the securenetwork may occur over a wired or wireless network, such as a wide areanetwork (WAN) or local area network (LAN) for example. As such, the newzone player may be configured to transmit the join message over the WANor LAN upon being powered up.

The WAN or LAN may be a secure or insecure network. In the case the WANor LAN is a secure network (separate from the secure playback systemnetwork), the new zone player may be pre-configured with securityparameters to communicate over the secure network. In one case, thepre-configured security parameters may be provided by the user whenacquiring the new zone player.

In another case, WAN or LAN may be an insecure network. In such a case,the new zone player may be pre-configured to transmit the join messageover a particular unsecure WAN or LAN network that devices in the securenetwork may also communicate over. For instance, the new device may beconfigured to transmit the join message over the unsecure networkaccording to a specific communication protocol. For example, the joinmessage may include specific prefixes. In this case, devices in thesecure network may be preconfigured to accept messages over the unsecurenetwork if the message follows the specific communication protocol.

In one case, the join message may be transmitted by the new zone playerwithout any specific action or input from a user after the new zoneplayer is powered up. In other words, no button-pressing or otheractions is required from the user (besides perhaps plugging the zoneplayer into a power outlet) for the zone player to transmit the joinmessage.

In another case, the join message may be automatically transmitted bythe new zone player or another zone player that may or may not be in thesecure network, upon a completion of a boot cycle by the zone playersubsequent to the initial powering up of the zone player. In otherwords, the user may reboot a zone player, which may or may not alreadybe in the secure network, and would not need to perform any additionalactions to cause the join message to be transmitted by the zone player.

In one case, the secure network may be a playback system including oneor more other playback devices such as the zone players 200, 202, 204,or 400, or one or more controllers such as controllers 300 and 500 asdescribed above. If one or more of the other zone players or controllersare within communicative range of the new zone player, the join messagemay be received by the playback system via one or more of the other zoneplayers or controllers in the secure network. In one example embodiment,the device (e.g., zone player or controller) that is withincommunicative range of the new zone player may forward the join messagesthat is received from new zone players to another device (e.g., zoneplayer or controller) in the playback system for processing.

In one example, the join message received from the new zone player mayinclude data identifying the new zone player. For instance, the joinmessage may indicate a serial number or model name of the new zoneplayer. The identifying data provided by the new zone player may then beused to determine how the new zone player may be added to the securenetwork, if the new zone player is allowed to join the secure network atall.

At block 804, the method 800 may involve determining a securityparameter to be used by the playback device to connect to the securenetwork. In one example, each zone player may use the same securityparameter to connect to the secure network. The security parameter mayinclude a password, and/or a specific communication protocol. In anotherexample, different zone players may be connected to the secure networkusing different security parameters. For instance, a controller devicemay be added to the secure network according to different securityparameters as a zone player. As stated above, the join message providedby the new zone player may be used to determine how the new zone playermay be added to the secure network, if the new zone player is allowed tojoin the secure network. As such, the identifying data may be used todetermine the security parameter to be used by the new zone player tojoin the secure network.

At block 806, the method 800 may involve transmitting to the playbackdevice a second message comprising the security parameter. Upondetermining the security parameters to be used by the new zone player tojoin the network, one of the one or more devices in the secure networkmay transmit to the new zone player a connection message (or “the secondmessage,” as recited above) including the security parameters toconfigure the new zone player's connection to the secure network. Thetransmission of the connection message from the secure network to thenew zone player may be over the same or a similar wired or wirelesscommunication protocol over which the new zone player transmitted thejoin message. The connection message may be encrypted to avoidunauthorized devices to determine the security parameter.

In one case, the connect message may include data identifying theplayback system of which the new zone player will become a part. Forexample, the connect message may include data indicating a householdidentifier (HHID), as discussed previously. In such a case, theconnection message may further include data identifying each of theother one or more devices already connected within the secure network.Such data identifying other devices in the secure network may allow thenew zone player to also establish individual connections to each of theother devices in the secure network.

At block 808, the method 800 may involve establishing a connectionbetween the playback device and the secure network. As suggested above,the connection between the new zone player and the secure network mayinvolve communication between the new zone player and other devices inthe playback system according to a specific communication protocol asdefined by the security parameters determined at block 804 and providedto the new zone player at block 806. In one example, upon establishingthe connection between the new zone player and the playback system, thenew zone player may transmit a confirmation message to the playbacksystem over the newly established secure connection to confirm that thenew zone player has joined the secure network. As such, a playbackdevice may be automatically added to a secure network of playbackdevices without any particular input or action from the user.

Also as suggested above, establishing a connection between the new zoneplayer and the secure network may involve the new zone playerestablishing individual connections with each of the other devices inthe secure network such that the new zone player may communicate witheach of the other devices in the secure network either directly orthrough one or more of the other devices also in the secure network. Inone example, establishing the connection between the new zone player andthe secure network may involve adding the new zone player to a meshnetwork as discussed previously, if the secure network of the playbacksystem is configured according to a mesh topology.

In discussions thus far, the playback system (or one or more deviceswithin the secure network) may receive the join message from the newzone player if the zone player and one or more devices in the securenetwork are within communicative range. This may involve the one or moredevices in the secure network to regularly be available to receive ajoin message in case there is a new zone player in communicative range.A method 830 may be provided such that the one or more devices in thesecure network may be configured to be available to receive a joinmessage when a join message from a new zone player is expected.

FIG. 8B shows a second example flow diagram of the method 830 forautomatically adding a playback device to a secure network, inaccordance with at least some embodiments described herein. Method 830shown in FIG. 8B presents an embodiment of a method that could be usedin the environments 100, 600, and 700 with the systems 200, 202, 204,300, 400, and 500 for example, in communication with one or moredevices, such as those illustrated in FIGS. 2-5. Method 830 may includeone or more operations, functions, or actions as illustrated by one ormore of blocks 832-842. Although the blocks are illustrated insequential order, these blocks may also be performed in parallel, and/orin a different order than those described herein. Also, the variousblocks may be combined into fewer blocks, divided into additionalblocks, and/or removed based upon the desired implementation.

At block 832, the method 830 may involve receiving at a controllerdevice, a configuration table from a server. The controller device, inthis case, may be a device such as the controllers 300 and 500 discussedpreviously in connection to FIGS. 3 and 5, and may be within the securenetwork of one or more other playback devices (or zone players)discussed above for rendering media in synchrony. In another case, thecontroller device may be in communication with one or more playbackdevices in the secure network, but not actually within the securenetwork of playback devices. In other words, the controller device maybe in a same HOUSEHOLD, but not within the same secure network as theone or more playback devices. As suggested previously in connection toreceiving a join message from a new zone player, playback devices withincommunicative range of one another may forward messages (such as join orconfigure messages) to each other. As such, the controller device mayreceive, via the other playback devices, the join message if thecontroller device is not within the secure network of one or moreplayback devices. In a further example, messages may be forwarded beyondthe present HOUSEHOLD. For instance, messages may be forwarded todevices in another HOUSEHOLD on a same local area network, or over theInternet.

As mentioned before, the configuration table may include a list of alldevices within the same HOUSEHOLD as the controller device, andrespective security parameters for each device on the list tocommunicate with one another within the secure network. In another case,as will be further discussed below, the configuration table may alsoinclude data indicating how devices in the playback system should beconfigured for rendering media.

In one example, the controller device may be configured to store a copyof the configuration table listing information associated with devicesin the playback system. In such a case, a previously storedconfiguration table may be deleted and replaced by a newly receivedconfiguration table when received by the controller device. In anothercase, the configuration table transmitted to the controller device mayonly include data associated with devices for which new configurationsexist, or with new devices to be added to the secure network. In otherwords, the configuration table transmitted to the controller device maybe a “change-list” instead of a full configuration table. In anotherexample, the controller may be configured to process and parse theconfiguration table, distribute or apply the data associated with thedevices in the playback system to the respective devices, andsubsequently delete rather than store the received configuration table.

As indicated previously, the server transmitting the configuration tablemay be one that is part of a cloud network, and in one case, theconfiguration table may be received by the controller device over a WANin communication with the cloud network. In one example, the server maybe the multimedia audio system server 720 described previously inconnection to FIG. 7. The transmission of the configuration table fromthe server to the controller device may be triggered by a number ofactions, or combination of actions. For instance, the transmission ofthe configuration table may be requested by the controller devices, orbe configured to occur at regular, predetermined intervals of time. Insome cases, the configuration table maybe transmitted only if a changein configuration for a device in the playback system is present,regardless of whether a request has been made by the controller device.In another instance, the configuration table may be “pushed” by theserver.

In one example, the controller device may request the configurationtable from the server by sending a request message to the server. Theserver, in response to receiving the request message, may then determineor compile a configuration table associated with the controller device(and other devices within the same secure network as the controllerdevice), and transmit the configuration table to the controller device.In some cases, the controller device may be configured to send therequest message at regular intervals such that the configuration tablemay remain up-to-date.

In another example, the server may transmit the configuration table tothe controller device without solicitation by the controller device.This may be the case when an update to data associated with devices inthe playback system is provided to the server, or if a new zone playerhas been acquired to become a device in the playback system, but thathas not been configured to join the secure network. In other words, thecloud network server may determine whether the controller device or anydevice in the secure network should receive an updated configurationtable, and transmit the configuration table accordingly.

In one example, the received configuration table may include dataassociated with devices that may or may not already be in the playbacksystem. At block 834, the method 830 may involve determining that theconfiguration table includes an entry corresponding to a playback devicethat is not joined to a secure network of the controller device. In oneexample, the controller device may compare the newly receivedconfiguration table against a previously stored configuration table todetermine if any entries for one or more new devices are present. Inanother example, the controller device may ping via the secure network,each device in the secure network and determine that a device, such as azone player listed in the configuration table, is not joined to thesecure network if no response to the ping is received. In a furtherexample, the configuration table may further include data indicatingthat a particular device listed in the configuration table is new.

After receiving the configuration table and identifying that a deviceshould be connected to the secure network, the controller may thereforeanticipate receiving a join message from the new device. At block 836,the method 830 may involve listening for a first message from theplayback device. The anticipated first message may in effect be the joinmessage indicating that the new zone player is available to join thesecure network, as discussed previously in connection to the method 800of FIG. 8A. Since the new zone player has not already joined the securenetwork, the join message may be received over an unsecure network, or anetwork such as a WAN or LAN, also as discussed previously.

In one case, zone players in the playback system may be configured tonot detect or receive messages over unsecure networks during regularoperation. In such a case, listening for the join message may involvethe zone players in the playback system becoming available to receivemessages over the unsecure network in anticipation of the join messagetransmitted over the unsecure network.

In another case, the new device may be configured to transmit the joinmessage over the unsecure network according to a specific communicationprotocol. For example, the join message may include specific prefixes.In this case, listening for the join message may involve acceptingmessages over the unsecure network if the message follows the specificcommunication protocol.

In either case, the controller device, or any other device in theplayback system may then be listening for the anticipated join message.At block 838, the method 830 may then involve receiving the firstmessage over the unsecure network, similar to block 802 of the method800 discussed above in connection to FIG. 8A, and at block 840, themethod 830 may involve transmitting, by the controller device, a secondmessage comprising a security parameter to be used by the playbackdevice to connect to the secure network, similar to block 806 of themethod 800 discussed above. In one example, the security parameter to beused by the playback device to connect to the secure network may beprovided in the configuration table. In another example, the securityparameter may be determined by the controller device or one or moreother devices in the playback system according to security parametersused by the controller device and/or other devices in the playbacksystem to connect to the secure network. Subsequently at block 842, themethod 830 may involve establishing a connection between the playbackdevice and the secure network using the security parameter, similar toblock 808 of the method 800 as discussed above. As such, a playbackdevice may be automatically added to a secure network of playbackdevices without any particular input or action from the user.

After a connection between the controller device and the secure networkhas been established, the configuration table may be deleted from thecontroller device. This, of course, may occur after any other securenetwork connections by or configuration updates to devices in theplayback system has been completed. In another case, the controllerdevice may remove from the configuration table, the entry correspondingto the playback device as soon as connection between the playback deviceand the secure network has been established, rather than after all otherconnections or configurations have been processed.

As indicated above, in addition to a list of devices that may join thesecure network and security parameters that may be used by the list ofdevices to join the secure network, the configuration table may alsoinclude data indicating how each device in the playback system should beconfigured for rendering media. FIG. 8C shows an example flow diagram ofa method 860 for automatically configuring a playback device in aplayback network, in accordance with at least some embodiments describedherein. Method 860 shown in FIG. 8C presents an embodiment of a methodthat could be used in the environments 100, 600, and 700 with thesystems 200, 202, 204, 300, 400, and 500 for example, in communicationwith one or more devices, such those illustrated in FIGS. 2-5. Method860 may include one or more operations, functions, or actions asillustrated by one or more of blocks 862-868. Although the blocks areillustrated in sequential order, these blocks may also be performed inparallel, and/or in a different order than those described herein. Also,the various blocks may be combined into fewer blocks, divided intoadditional blocks, and/or removed based upon the desired implementation.

At block 862, the method 860 may involve determining that a playbackdevice listed in a configuration table is not already configured foroperation. As with the discussion of method 830, the configuration tablein this discussion of the method 860 may be received from a cloudserver, such as the multimedia audio system server 720 in FIG. 7, over awired or wireless network, such as a WAN or LAN. In one example,determining that the playback device listed in the configuration tableis not configured for operation may be similar to determining that theconfiguration table includes an entry corresponding to a playback devicethat is not joined to a secure network of the controller device, asdiscussed above in connection to block 834 of the method 830. Forinstance, the controller device may receive a configuration tableindicating a new playback device that is not joined to the securenetwork of the controller device. In this case, if the new playbackdevice is not joined to the secure network, then the new playback devicemay not have been configured for operation to render media in synchronywith other devices in the playback system. In another case, if newfirmware is available the devices in the playback system, and one ormore devices in the playback system has not been upgraded with the newfirmware, then the one or more devices that have not been updated may beconsidered as not having been configured for operation. In a furthercase, the controller device may be configured to ping each device in theplayback system for present configuration settings, and if a device doesnot respond, or responds with a configuration that does not match thatlisted in the configuration table for the particular device, then theparticular device may be considered as not having been configured foroperation.

Upon determining that a playback device in the playback system is notconfigured for operation, the controller device and/or other devices inthe playback system may then listen for a configuration message from theunconfigured device indicating that the device is available to beconfigured. If the unconfigured device is already connected to thesecure network, then the controller device may listen for theconfiguration message over the secure network. If the unconfigureddevice is not already connected to the secure network, then thecontroller device may listen for the configuration message over anunsecure network, similar to how the controller device may listen for ajoin message as described above in connection to the method 830 of FIG.8B. In this case, the configuration message may be part of a samemessage as the join message.

At block 864, the method 860 may involve receiving from the playbackdevice a first message indicating that the playback device is availableto be configured. As stated above, the configuration message (or the“first message,” as recited above) may be received along with, or aspart of the join message from the new playback device over the unsecuredwired or wireless network. In another example, the configuration messagemay be received after the join message. In this case, the configurationmessage may be transmitted from the new playback device over the securenetwork after the new playback device has joined the secure network.

In response to receiving the configuration message, at block 866 ofmethod 860 may involve transmitting to the playback device, a secondmessage comprising configuration data (i.e. setup information) for theplayback device. In other words, the controller device (and/or one ormore of the other devices in the playback system) may transmit asettings message (the “second message”) to the new zone player toprovide configuration data to the new playback device upon receiving theconfiguration message indicating that the new playback device isavailable to be configured. The information in the settings message maybe derived from the configuration table. In the case the configurationmessage is received along with the join message, or before a secureconnection has been established between the new playback device and theplayback system, the settings message may be transmitted to the newplayback device along with, or as a part of the connection message thatincludes security parameters for the new playback device to join thesecure network.

In another example, block 866 may involve transmitting the settingsmessage to the new playback device (or, as discussed previously, anydevice in the playback system that is not configured for operation inthe secure network) whether or not the configuration message has beenreceived. In other words, the controller device may push the settingsmessage to any device that may require an initial configuration or aconfiguration update.

At block 868, the method 860 may involve causing the playback device tobe configured according to the configuration data. Upon receiving thesettings message from the controller device, the new playback device maynow be configured according to the configuration data provided via thesettings message. As indicated, the new playback device, or any devicein the secure network may be configured to render media in synchronywith other devices in the secure network. As such, the configurationdata for configuring a playback device may indicate audio playbacksettings for the playback device.

In one example, the new playback device may be intended for use as acomponent of a bonded zone of playback devices. As suggested previously,a bonded zone of playback devices may involve a group of two or moreplayers in a designated zone that renders the same or different channelsof an audio signal in a synchronized fashion, such that the playersrender audio content with no (or substantially no) audible delays orhiccups. Players may be grouped and ungrouped into bonded zonesdynamically, and bonded zones may be further grouped with other playersand/or bonded zones to create another bonded zone. Bonded zones mayfurther be described in terms of a “paired player” or a “consolidatedplayer”.

A paired player may involve a bonded zone, whereby the players may playdifferent audio channels of audio content. For example, a “stereo pair”is a paired player created by grouping two players in a bonded zone toplay 2-channel audio. In one case, bonding the two players in the stereopair may result in a left channel player and a right channel player. Aconsolidated player may involve a bonded zone, whereby the players aregrouped to render a frequency range, or portion of a frequency range ofaudio content. In one example, a consolidated player may be created bygrouping a full-range player with a low-frequency player (e.g.subwoofer). In this case, the full-rage player may be configured torender the mid and high frequency range of the audio content, while thelow-frequency player may be configured to render just the low-frequencyrange of the audio content.

Referring back to block 868, in the case the new playback device isintended for use as one of a stereo pair to render media in synchronywith another device in the secure network, the configuration data mayindicate that the new playback device will function as either a left orright channel speaker. In one case, the new playback device may beconfigured such that the new playback device will render a left channelaudio component of media, for example. In such a case, a zone playeralready in the secure network may also be re-configured to render theother, right channel audio component of media as a result of theaddition and configuration of the new playback device to create thestereo pair.

The configuration data may also indicate audio equalization settings forthe new playback device, and configuration of the new playback devicemay also involve changing the audio equalization settings of the newplayback device accordingly. In such a case, if the new playback deviceis also being added to a bonded zone, the audio equalization settings ofone or more of the other zone players in the bonded zone may also beadjusted as a result.

In addition to settings associated with audio rendering of the newplayback device, the configuration data may also indicate user interfaceand user experience related settings. For example, the configurationdata may include a user-readable name to be assigned to the new playbackdevice. As such, the new playback device may be identified as theuser-readable name when the user sees the new playback device on acontrol interface for the playback system. Similarly, the configurationdata may include registration information for one or more music servicesto be registered to the playback system, and accordingly, configurationof the new playback device may involve setting up the new playbackdevice to access the one or more music services. Other exampleconfiguration settings may also be possible.

Upon completion of configuration according to the configuration data,the new zone player may then transmit a confirmation message to thecontroller device, or one or more other devices in the playback systemindicating that configuration was completed. As such, a playback devicemay be automatically configured for operation within a secure network ofplayback devices without any particular input or action from the user.

As indicated above, the configuration data in the configuration tableprovided to the controller device and based upon to configure a newplayback device (or other devices already within the secure network) maybe, to an extent, determined based on previous input from the user. Inone example, if the user purchased the new playback device from anonline retailer on the World Wide Web, the user may be prompted duringcheck-out to provide the configuration data, or information that may bebased upon to determine the configuration data. In another example, ifthe user purchased the new playback device at a store, the user may beprompted at the point-of-sale (by a sales associate, for example) toprovide the configuration data, or information that may be based upon todetermine the configuration data. In a further example, the user may beprompted via email shortly after acquiring the new playback device(either at the store or from an online retailer) to provide thecorresponding configuration data or information via a web interfacelinked to in the email.

Information that may be used to determine the configuration data mayinclude what the new playback device is intended for (e.g. part of abonded zone or stereo pair), the names of other players that the newplayback device will be connected with, where the new zone player willbe used (e.g. kitchen, bedroom, living room), what type of music theuser enjoys (e.g. rock, jazz, classical), if the device is to be part ofa bonded zone, or the name of the playback device. The type of music theuser enjoys may be based upon to determine audio equalization settingsfor the new playback device, as discussed above. In addition, the usermay also enter identifying information of the user such as a username oremail such that media services that the user has access to may bedetermined, and configuration data for registering the new playbackdevice for access to the media services may be determined. In somecases, the identifying information may be automatically determined withminimal or no input from the user. For instance, if the user purchasedthe new playback device using a personal device such as a smart phone orcomputer having the identifying information stored thereon, theidentifying information may be automatically retrieved from thecontroller application.

To further describe the automatic setup of playback device, includingthe joining of a secure network and configuration of the playback devicefor media playback, a series of scenarios are presented in FIGS. 9A, 8B,and 9C to illustrate an example acquisition and configuration of a newplayback device.

FIG. 9A shows a first scenario for adding a playback device to, andconfiguring the playback device for a secure playback network. As shown,the first scenario may involve a cloud network 971, a warehouse 940, anda household 950. The warehouse 940 may be a warehouse for amanufacturer, for a store, or for an online retailer, and may contain anumber of playback devices including a zone player 902. The householdmay include a number of playback devices including a controller 930 andzone players 922, 924, 926, and 928. As shown, the controller 930 andzone players 922, 924, 926, and 928 may be in communication with eachother over a secure network 961.

In the first scenario, the zone player 902 may be acquired by a user tobe used in the household 950. Upon acquiring the zone player 902, theuser may be prompted to provide information about the user, andinformation relating to how the zone player 902 will be used. Theanswers provided by the user may then be associated with specificallythe zone player 902. For instance, a serial number of the zone player902 and the answers provided by the user may be provided to the cloudnetwork 971, where the serial number and the answers may becomeassociated, and where configuration data may be determined for the zoneplayer 902. In this case, the user may provide information indicatingthat the zone player 902 will be added to the secure network 961 in thehousehold 950. As such, configuration data associated with the zoneplayer 902 may indicate that the zone player 902 will be added to thesecure network 961.

The configuration data may then be provided by the cloud network 971 tothe secure network 961, or to a device in the secure network 961, suchas the controller 930. Referring back to the discussions of the methods800 and 830 described in connection to FIGS. 8A and 8B, the securenetwork 961 (and devices within the secure network 961) may then listenfor a join message from the new zone player 902.

FIG. 9B shows a second scenario for adding a playback device to, andconfiguring the playback device for a secure playback network. As shown,the new zone player 902 may have arrived at the household 950, beenpowered up by the user, and may now be in communicative range of thesecure network 961. The zone player 902 may then transmit the joinmessage to the controller 930 over an unsecure network. In response, thecontroller 930 may transmit a connection message to the zone player 902with information on how the zone player 902 may join the secure network.In another example, the zone player 902 may also transmit aconfiguration message to the controller 930 indicating that the zoneplayer 902 is available to be configured. In this case, the controller930 may also transmit a settings message with information on how thezone player 902 should be configured.

FIG. 9C shows a third scenario for adding a playback device to, andconfiguring the playback device for a secure playback network. As shown,the zone player 902 may have successfully joined the secure network 961and may be communicating with any of the devices 930, 922, 924, 926, and928 over the secure network 691. If the zone player 902 has not alreadybeen configured, the zone player 902 may then transmit a configurationmessage over the secure network 961 to one or more of the other devicesin the secure network 961 and subsequently receive a settings messageindicating how the zone player 902 should be configured. As such, asidefrom providing configuration data or information indicating an intendeduse of the new zone player 902 when first acquiring the zone player, andsubsequently powering up the new zone player 902 within the household950, no additional action or input from the user is required for the newzone player 902 to join the secure network 961, and be configured torender media in synchrony with other devices in the secure network 961.

FIG. 10 further shows an example interaction 950 between devices whenadding a playback device to, and/or configuring the playback device fora secure playback network of devices. FIG. 10 includes the new zoneplayer 902, the controller 930, and zone players 922, 924, 926, and 928similar to that shown in FIGS. 9A to 9C, and further includes an accesspoint 952, a first secure network 954, and a second secure network 956.As shown, zone players 924, 928, and 926 may communicate wirelessly witheach other over the first secure network 954. Zone players 926 and 922may communicate over a wired connection, and zone player 922 may becoupled to the access point 952 to further be in communication with thecontroller 930 wirelessly over the second secure network 956. As shownin this example, a HOUSEHOLD may include more than one secure network.

When the new zone player 902 arrives at the household, as described inconnection to FIGS. 9A, 9B, and 9C, the new zone player 902 maybroadcast a join message indicating an availability to join the firstsecure network 954. In one example, the join message may be received byany one or more of the zone players shown in FIG. 10, including thecontroller 930. In the case the controller 930 receives the joinmessage, the controller 930 may provide security parameters for joiningthe first secure network 954 to the new zone player 902 directly.

In another example, the new zone player 902 might not be withincommunicative range of the controller device 930, or the new zone player902 is available to join the secure network 954, which the controllerdevice 930, as shown, is not a part of. In either case, if the new zoneplayer 902 is within communicative range of any of the other zoneplayers in the HOUSEHOLD, such as zone player 926 as shown, the joinmessage received by the zone player 926 may be forwarded to thecontroller 930 via zone player 922 and the access point 952 using thewired communication, and over the second secure network 956 wirelessly,Upon receiving the join message, the controller 930 may communicate tothe new zone player 902 security parameters for joining the first securenetwork 954 via the second secure network 956, the access point 952, andzone players 926 and 922.

Subsequently, the new zone player may join the first secure network 954.One having ordinary skill in the art will appreciate that the joinmessage may similarly be received by any of the other zone players andforwarded to the controller 930. As previously discussed, a similarchain of communication may also be implemented for configuring the newzone player 902 based on a configuration table received by thecontroller 930.

VIII. Conclusion

The descriptions above disclose various example systems, methods,apparatus, and articles of manufacture including, among othercomponents, firmware and/or software executed on hardware. However, suchexamples are merely illustrative and should not be considered aslimiting. For example, it is contemplated that any or all of thesefirmware, hardware, and/or software components can be embodiedexclusively in hardware, exclusively in software, exclusively infirmware, or in any combination of hardware, software, and/or firmware.Accordingly, while the following describes example systems, methods,apparatus, and/or articles of manufacture, the examples provided are notthe only way(s) to implement such systems, methods, apparatus, and/orarticles of manufacture.

As suggested above, the present application involves causing a newplayback device to be automatically added to a secure network andconfigured to render media in synchrony with other devices in the securenetwork without any action by a user. In one aspect, a method isprovided. The method involves receiving, by a controller device, aconfiguration table from a server over a wide area network, determining,by the controller device, that the configuration table includes an entrycorresponding to the playback device that is unconfigured for playback,and responsively, transmitting from the controller device to theplayback device, a first message comprising setup information for theplayback device.

In another aspect, a controller device is provided. The controllerdevice includes processor, memory, and instructions stored on thememory. The instructions are executable by the processor to performfunctions including receiving a configuration table from a server over awide area network, determining that the configuration table includes anentry corresponding to the playback device that is unconfigured forplayback, and responsively, transmitting to the playback device, a firstmessage comprising setup information for the playback device

In yet another aspect, a non-transitory computer readable medium havinginstructions stored thereon is provided. The instructions are executableby a computing device to cause the computing device to perform functionsincluding receiving, by a controller device, a configuration table froma server over a wide area network, determining, by the controllerdevice, that the configuration table includes an entry corresponding tothe playback device that is unconfigured for playback, and responsivelytransmitting, by the controller device to the playback device, a firstmessage comprising setup information for the playback device.

Additionally, references herein to “embodiment” means that a particularfeature, structure, or characteristic described in connection with theembodiment can be included in at least one example embodiment of theinvention. The appearances of this phrase in various places in thespecification are not necessarily all referring to the same embodiment,nor are separate or alternative embodiments mutually exclusive of otherembodiments. As such, the embodiments described herein, explicitly andimplicitly understood by one skilled in the art, can be combined withother embodiments.

The specification is presented largely in terms of illustrativeenvironments, systems, procedures, steps, logic blocks, processing, andother symbolic representations that directly or indirectly resemble theoperations of data processing devices coupled to networks. These processdescriptions and representations are typically used by those skilled inthe art to most effectively convey the substance of their work to othersskilled in the art. Numerous specific details are set forth to provide athorough understanding of the present disclosure. However, it isunderstood to those skilled in the art that certain embodiments of thepresent disclosure can be practiced without certain, specific details.In other instances, well known methods, procedures, components, andcircuitry have not been described in detail to avoid unnecessarilyobscuring aspects of the embodiments. Accordingly, the scope of thepresent disclosure is defined by the appended claims rather than theforgoing description of embodiments.

When any of the appended claims are read to cover a purely softwareand/or firmware implementation, at least one of the elements in at leastone example is hereby expressly defined to include a tangible mediumsuch as a memory, DVD, CD, Blu-ray, and so on, storing the softwareand/or firmware.

We claim:
 1. A first playback device comprising: a network interface;one or more processors; and data storage having instructions encodedtherein, wherein the instructions, when executed by the one or moreprocessors, cause the first playback device to perform functionscomprising: receiving, via the network interface from a second playbackdevice over an unsecure network, a message indicating that the secondplayback device is available to join a playback network, wherein thefirst playback device is connected to the playback network; based on apre-existing configuration table, determining an audio settingcorresponding to a playback configuration for the second playbackdevice, wherein the playback configuration comprises the second playbackdevice playing back audio synchronously with the first playback devicein the playback network, wherein the determined audio setting is storedin the pre-existing configuration table prior to the first playbackdevice receiving the message indicating that the second playback deviceis available to join the playback network; and transmitting, via thenetwork interface to the second playback device, one or more messagesinstructing the second playback device to apply the determined audiosetting upon joining the playback network, wherein applying thedetermined audio setting comprises forming the playback configurationwith the first playback device to play back audio synchronously.
 2. Thefirst playback device of claim 1, wherein the functions further comprisetransmitting one or more messages instructing the second playback deviceto join the playback network using security parameters of the playbacknetwork.
 3. The first playback device of claim 1, wherein applying thedetermined audio setting further comprises adjusting a volume level ofthe second playback device.
 4. The first playback device of claim 1,wherein the functions further comprise: receiving, from the secondplayback device, data identifying the second playback device, andwherein determining the audio setting corresponding to the secondplayback device comprises determining the audio setting further based onthe data identifying the second playback device.
 5. The first playbackdevice of claim 3, wherein the data identifying the second playbackdevice comprises one or more of: (a) a serial number of the secondplayback device, (b) a model name of the second playback device, or (c)a model number of the second playback device.
 6. The first playbackdevice of claim 1, wherein determining an audio setting corresponding tothe second playback device comprises: identifying, in the pre-existingconfiguration table, a zone group corresponding to the second playbackdevice; and determining, as the audio setting corresponding to thesecond playback device, an audio setting corresponding to the zonegroup.
 7. The first playback device of claim 1, wherein the pre-existingconfiguration table is maintained in data storage at a cloud server, andwherein the functions further comprise: receiving, via the networkinterface from the cloud server, data representing the playbackconfiguration for the second playback device.
 8. The first playbackdevice of claim 6, wherein the functions further comprise: in responseto receiving the message indicating that the second playback device isavailable to join the playback network, transmitting, to the cloudserver, a request for the pre-existing configuration table, wherein thefirst playback device receives, from the server, the data representingthe playback configuration for the second playback device beforedetermining the audio setting.
 9. A method to be performed by a firstplayback device, the method comprising: receiving, via a networkinterface from a second playback device over an unsecure network, amessage indicating that the second playback device is available to joina playback network, wherein the first playback device is connected tothe playback network; based on a pre-existing configuration table,determining an audio setting corresponding to a playback configurationfor the second playback device, wherein the playback configurationcomprises the second playback device playing back audio synchronouslywith the first playback device in the playback network, wherein thedetermined audio setting is stored in the pre-existing configurationtable prior to the first playback device receiving the messageindicating that the second playback device is available to join theplayback network; and transmitting, via the network interface to thesecond playback device, one or more messages instructing the secondplayback device to apply the determined audio setting upon joining theplayback network, wherein applying the determined audio settingcomprises forming the playback configuration with the first playbackdevice to play back audio synchronously.
 10. The method of claim 9,wherein the functions further comprise transmitting one or more messagesinstructing the second playback device to join the playback networkusing security parameters of the playback network.
 11. The method ofclaim 9, wherein applying the determined audio setting further comprisesadjusting a volume level of the second playback device.
 12. The methodof claim 9, further comprising: receiving, from the second playbackdevice, data identifying the second playback device, and whereindetermining the audio setting corresponding to the second playbackdevice comprises determining the audio setting further based on the dataidentifying the second playback device.
 13. The method of claim 11,wherein the data identifying the second playback device comprises one ormore of: (a) a serial number of the second playback device, (b) a modelname of the second playback device, or (c) a model number of the secondplayback device.
 14. The method of claim 9, wherein determining an audiosetting corresponding to the second playback device comprises:identifying, in the pre-existing configuration table, a zone groupcorresponding to the second playback device; and determining, as theaudio setting corresponding to the second playback device, an audiosetting corresponding to the zone group.
 15. The method of claim 9,wherein the pre-existing configuration table is maintained in datastorage at a cloud server, and wherein the method further comprises:receiving, via the network interface from the cloud server, datarepresenting the playback configuration for the second playback device.16. The method of claim 14, further comprising: in response to receivingthe message indicating that the second playback device is available tojoin the playback network, transmitting, to the cloud server, a requestfor the pre-existing configuration table, wherein the first playbackdevice receives, from the server, the data representing the playbackconfiguration for the second playback device before determining theaudio setting.
 17. A tangible non-transitory computer-readable mediahaving instructions encoded therein, wherein the instructions, whenexecuted by one or more processors, cause a first playback device toperform a method comprising: receiving, via a network interface from asecond playback device over an unsecure network, a message indicatingthat the second playback device is available to join a playback network,wherein the first playback device is connected to the playback network;based on a pre-existing configuration table, determining an audiosetting corresponding to a playback configuration for the secondplayback device, wherein the playback configuration comprises the secondplayback device playing back audio synchronously with the first playbackdevice in the playback network, wherein the determined audio setting isstored in the pre-existing configuration table prior to the firstplayback device receiving the message indicating that the secondplayback device is available to join the playback network; andtransmitting, via the network interface to the second playback device,one or more messages instructing the second playback device to apply thedetermined audio setting upon joining the playback network, whereinapplying the determined audio setting comprises forming the playbackconfiguration with the first playback device to play back audiosynchronously.
 18. The tangible non-transitory computer-readable mediaof claim 17, wherein applying the determined audio setting furthercomprises adjusting a volume level of the second playback device. 19.The tangible non-transitory computer-readable media of claim 17, whereinthe pre-existing configuration table is maintained in data storage at acloud server, and wherein the method further comprises: in response toreceiving the message indicating that the second playback device isavailable to join the playback network, transmitting, to the cloudserver, a request for the pre-existing configuration table; and beforedetermining the audio setting, receiving, via the network interface fromthe cloud server, data representing the playback configuration for thesecond playback device.
 20. The tangible non-transitorycomputer-readable media of claim 17, further comprising: receiving, fromthe second playback device, data identifying the second playback device,wherein determining the audio setting corresponding to the secondplayback device comprises determining the audio setting further based onthe data identifying the second playback device, and wherein the dataidentifying the second playback device comprises one or more of: (a) aserial number of the second playback device, (b) a model name of thesecond playback device, or (c) a model number of the second playbackdevice.